MP - Monitor Channel
--------------------

For speciated data, observations of multiple parameters can result from the analysis of a sample from a single channel. For example, concentrations of several different metals can be determined by analyzing one filter from one channel of a sampler. So the analysis of one sample from one channel can generate data that is stored under multiple AQS monitors.

The purpose of this transaction is to allow the mapping of parameters to sampler channels. Once this relationship is established, it will be possible to submit flow data once for a channel, rather than having to submit the same flow data once for each monitor associated with the channel.

After establishing the Monitor Channel records, flow data at the channel level can be submitted using the Speciation Semi-Annual Flow Rate Audit transaction.


.. LOOK AT SITE SAMPLER CHANNEL EXAMPLES

Examples:

.. code-block:: text
   :caption: MP transaction in default mode

   MP|I|17|031|4201|88102|5|MET-ONE-A|1|20021011|

.. code-block:: text
   :caption: MP transaction in Tribal mode

   MP|I|TT|W44|0901|88102|5|MET-ONE-A|1|20010815|



Format
^^^^^^

.. list-table:: MP - Monitor Channel transaction format
   :widths: 1 5 15 4 3 1
   :header-rows: 1


   * - Seq.
     - Name
     - Description
     - Formatting Rules
     - Required
     - Key
   * - 1
     - `Transaction Type <Transaction%20Type.html>`_
     - Monitor Channel Info transaction identifier.
     - Must = MP
     - Always
     - 
   * - 2
     - `Action Indicator <Action%20Indicator%20for%20Transaction.html>`_
     - Indicator for Insert, Update, or Delete action.
     - Must = I, U, or D
     - Always
     - 
   * - 3
     - `State Code / Tribal Indicator <State%20Code.html>`_
     - The FIPS state code of the monitor, or "TT" to indicate that the next field on the transaction is a Tribal code.
     - Must exist in STATES Reference Table or be 'TT' for Tribal Site
     - Always
     - Y
   * - 4
     - `County Code / Tribal Code <County%20Code.html>`_
     - The FIPS County Code of the site.  If the previous field on the transaction contains "TT", then the Tribal Code of the site.
     - Must exist in COUNTIES (for state) or TRIBAL_AREAS Reference table
     - Always
     - Y
   * - 5
     - `Site Number <Site%20Number.html>`_
     - Four digit number to uniquely identify site in county and/or tribe.
     - Must exist in SITES table with {State Code, county Code} or Tribal Code
     - Always
     - Y
   * - 6
     - `Parameter Code <Parameter%20Code.html>`_
     - The AQS parameter code assigned to the monitor in AQS.
     - Must exist in PARAMETERS reference table.
     - Always
     - Y
   * - 7
     - `POC <POC.html>`_
     - Parameter Occurrence Code:  One or two digit number identifying a specific monitor for a parameter at the site.  
     - Must exist in MONITOR table for non-Insert actions.
     - Always
     - Y
   * - 8
     - `Sampler ID <Sampler%20ID.html>`_
     - The user's unique name or id for the sampler at the site.
     - Must exist for Site in database
     - Always
     - Y
   * - 9
     - `Sampler Channel Number <Sampler%20Channel%20Number.html>`_
     - Number assigned to channel on sampler
     - Must be defined for Sampler in database
     - Always
     - Y
   * - 10
     - `Begin Date <Monitor%20Channel%20Begin%20Date.html>`_
     - Beginning of date range where the monitor (parameter + POC) is associated with the channel.
     - YYYYMMDD.
     - Always
     - Y
   * - 11
     - `End Date <Monitor%20Channel%20End%20Date.html>`_
     - End of date range where the monitor (parameter + POC) is associated with the channel.
     - YYYYMMDD.
     - No
     -